authselect/1.2.x-authselect-profiles.5.adoc — English @ Fedora Weblate: The purpose of this PAM stack is to provide a …

Source string Source string

English

The purpose of this PAM stack is to provide a common place for all PAM modules which should be called after the stack configured in system-auth or the other common PAM configuration files. It is included from all individual service configuration files that provide login service with shell or file access. _NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file._

Needs editing

The string is read only.

Skip

	English	Actions
	{AUTHSELECT_PROFILE_DIR}
	Read-only directory containing profiles shipped together with authselect.
	{AUTHSELECT_VENDOR_DIR}
	Read-only directory for vendor-specific profiles that can override the ones in _default_ directory.
	{AUTHSELECT_CUSTOM_DIR}
	Place for administrator-defined profiles.
	PROFILE FILES
	Each profile consists of one or more of these files which provide a mandatory profile description and describe the changes that are done to the system.
	README
	Description of the profile. The first line must be a name of the profile.
	system-auth
	PAM stack that is included from nearly all individual service configuration files.
	password-auth, smartcard-auth, fingerprint-auth
	These PAM stacks are for applications which handle authentication from different types of devices via simultaneously running individual conversations instead of one aggregate conversation.
	postlogin
	The purpose of this PAM stack is to provide a common place for all PAM modules which should be called after the stack configured in system-auth or the other common PAM configuration files. It is included from all individual service configuration files that provide login service with shell or file access. _NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file._
	nsswitch.conf
	Name Service Switch configuration file. Only maps relevant to the profile must be set. Maps that are not specified by the profile are included from {AUTHSELECT_CONFIG_DIR}/user-nsswitch.conf.
	dconf-db
	Changes to dconf database. The main uses case of this file is to set changes for gnome login screen in order to enable or disable smartcard and fingerprint authentication.
	dconf-locks
	This file define locks on values set in dconf database.
	CONDITIONAL LINES
	Each of these files serves as a template. A template is a plain text file with optional usage of several operators that can be used to provide some optional profile features.
	{continue if "feature"}
	Immediately stop processing of the file unless "feature" is defined (the rest of the file content will be removed). If "feature" is defined, the whole line with this operator will be removed and the rest of the template will be processed.
	{stop if "feature"}
	Opposite of "continue if". Immediately stop processing of the file if "feature" is defined (the rest of the file content will be removed). If "feature" is not defined, the whole line with this operator will be removed and the rest of the template will be processed.
	{include if "feature"}
	Include the line where this operator is placed only if "feature" is defined.
	{exclude if "feature"}

Loading…

minerva Comment added authselect 1.2.x-authselect-profiles.5.adoc English	The source text is unintelligible. An interpretation is below, but it can be false. The purpose of this PAM stack is to provide a common place for all PAM modules. It should be called after the stack has been configured with system-auth or with the other common PAM configuration files. The PAM stack is included in all configuration files that relate to individual services that provide a login service for access to a shell or to files. NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file. a year ago
minerva Comment removed authselect 1.2.x-authselect-profiles.5.adoc English	Comment removed a year ago
minerva Comment added authselect 1.2.x-authselect-profiles.5.adoc English	The source text is unintelligible. An interpretation is below, but it can be false. The purpose of this PAM stack is to provide a common place for all PAM modules. It should be called after the stack has been configured with system-auth or with the other common PAM configuration files. It is included in all service configuration files that relate to individual services that provide a login service for access to a shell or to files. NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file. a year ago
None String updated in the repository authselect 1.2.x-authselect-profiles.5.adoc English	English The purpose of this PAM stack is to provide a common place for all PAM modules which should be called after the stack configured in system-auth or the other common PAM configuration files. It is included from all individual service configuration files that provide login service with shell or file access. _NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file._ English 465 characters edited Current translation Read only The purpose of this PAM stack is to provide a common place for all PAM modules which should be called after the stack configured in system-auth or the other common PAM configuration files. It is included from all individual service configuration files that provide login service with shell or file access. _NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file._ 2 years ago

Browse all string changes

minerva

Source string comment

The source text is unintelligible. An interpretation is below, but it can be false.

The purpose of this PAM stack is to provide a common place for all PAM modules. It should be called after the stack has been configured with system-auth or with the other common PAM configuration files. The PAM stack is included in all configuration files that relate to individual services that provide a login service for access to a shell or to files. NOTE: the modules in the postlogin configuration file are executed regardless of the success or failure of the modules in the system-auth configuration file.

a year ago

Things to check

Comments

There is 1 unresolved comment for this string.

View

Glossary

English	English
No related strings found in the glossary.

String information

Source string description

type: Plain text

Flags

c-format, read-only

Source string location

./src/man/authselect-profiles.5.adoc:54

String age

2 years ago

Last updated

11 months ago

Source string age

2 years ago

Translation file

src/man/po/authselect-profiles.5.adoc.pot, string 23